refactor(crypto-keys): Extract foundation crypto keys#1162
Merged
Conversation
Move the crypt and keys main-source boundary into a new internal leaf module and re-home the remaining support blockers needed for the extraction. Keep the new BucketTools bridge compatible with inherited file-bucket split methods and pooled RAF restore, and add focused regression tests for those reflective paths.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Summary
:foundation-crypto-keysand wire it into the root buildnetwork.crypta.cryptandnetwork.crypta.keysboundary into that leaf without changing package names:foundation-support, and moveBucketToolsplusPrependLengthOutputStreaminto:foundation-crypto-keysBucketToolsbridge for inheritedFileBucket.split(int)lookup and pooled RAF restoreBucketToolsValidation
Notes